home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000063_yackd@alaska.et.byu.edu_Mon Oct 4 12:06 MDT 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
2KB
Received: from yvax.byu.edu by maine.et.byu.edu; Mon, 4 Oct 93 12:06:25 -0600
Return-Path: <yackd@alaska.et.byu.edu>
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H3PPQQK8J4936I6I@yvax.byu.edu>; Mon, 4 Oct 1993 12:04:24 MDT
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H3PPQMZ5JK936GKL@yvax.byu.edu>; Mon, 4 Oct 1993 12:04:19 MDT
Received: from yvax2.byu.edu by alaska.et.byu.edu; Mon, 4 Oct 93 12:05:59 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H3PPQ657VK94JM87@yvax.byu.edu>; Mon, 4 Oct 1993 12:03:57 MDT
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H3PPQ2RV28936IJN@yvax.byu.edu>; Mon, 4 Oct 1993 12:03:52 MDT
Received: by alaska.et.byu.edu; Mon, 4 Oct 93 12:05:41 -0600
Date: Mon, 04 Oct 1993 12:05:41 -0600
From: yackd@alaska.et.byu.edu (Don Yacktman)
Subject: Re: Making objects distributable
To: misckit@byu.edu
Message-Id: <9310041805.AA16013@alaska.et.byu.edu>
Content-Transfer-Encoding: 7BIT
Status: RO
> One thing I've noticed so far, and have found to be of great help,
> is that the objects in the misc kit have the encodeUsing:, decodeUsing:,
> and encodeRemotelFor:freeAfterEncoding:isBycopy: methods to allow them
> to be used in Distributed Objects.
This is, of course, no accident. I use these objects for DO type stuff
a lot, and so...
> I'd like to see most of the utility
> type objects (non-interface objects) have the capability to be distributed,
> by copy if necessary. It's sort of like asking each object to have read:
> and write: methods.
Yep. I agree. Where possible, DO and -read:/-write: methods should be
implemented. It's a big help and something that is really needed in
order to use the objects to their full capacities. Being able to send
stuff bycopy is a great way to wrap up packets of data for transmission
between apps... so, I concur that these methods ought to be present in
most cases. (For some objects, it wouldn't be useful, but most non-
interface objects ought to be DO-ready.) Of course, seeing as I'm the
one who put the DO methods in there in the first place, my position
on this shouldn't be any sort of surprise. :-)
Later,
-don